Skip to content

[improve](cloud) Report read/write conflict range #59437

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
gavinchou merged 1 commit into from
Jan 5, 2026
Merged

[improve](cloud) Report read/write conflict range #59437

gavinchou merged 1 commit into from
Jan 5, 2026

Conversation

@w41ter
Copy link
Contributor

@w41ter w41ter commented Dec 29, 2025

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason

  • Behavior changed:

    • No.
    • Yes.

  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@w41ter w41ter requested a review from gavinchou as a code owner December 29, 2025 02:50
@w41ter w41ter added the cloud label Dec 29, 2025
@w41ter w41ter requested a review from dataroaring as a code owner December 29, 2025 02:50
@Thearas
Copy link
Contributor

Thearas commented Dec 29, 2025

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Dec 29, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 29, 2025

PR approved by at least one committer and no changes requested.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 29, 2025

PR approved by anyone and no changes requested.

@w41ter
Copy link
Contributor Author

w41ter commented Dec 30, 2025

run buildall

@doris-robot
Copy link

doris-robot commented Dec 30, 2025

Cloud UT Coverage Report

Increment line coverage 83.78% (93/111) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 79.56% (1775/2231)
Line Coverage 64.86% (31417/48441)
Region Coverage 65.45% (15646/23907)
Branch Coverage 55.99% (8305/14832)

@gavinchou gavinchou merged commit 5e0c87f into apache:master Jan 5, 2026
30 of 31 checks passed
github-actions bot pushed a commit that referenced this pull request Jan 5, 2026
@w41ter
[improve](cloud) Report read/write conflict range (#59437)
8be5160
@github-actions github-actions bot mentioned this pull request Jan 5, 2026
Merged
yiguolei pushed a commit that referenced this pull request Jan 7, 2026
@github-actions @w41ter
branch-4.0: [improve](cloud) Report read/write conflict range #59437 (#…
a10f565 
…59577)

Cherry-picked from #59437

Co-authored-by: walter <maochuan@selectdb.com>
@w41ter w41ter deleted the cloud/improve/report_read_write_conflict_ranges branch January 8, 2026 03:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@gavinchou gavinchou gavinchou approved these changes

@dataroaring dataroaring Awaiting requested review from dataroaring dataroaring is a code owner

+1 more reviewer

@Yukang-Lian Yukang-Lian Yukang-Lian approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by one committer. cloud dev/3.1.x dev/3.1.x-conflict dev/4.0.3-merged reviewed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@w41ter @Thearas @doris-robot @gavinchou @Yukang-Lian @yiguolei